From: kaf24@scramble.cl.cam.ac.uk Date: Thu, 13 May 2004 07:29:04 +0000 (+0000) Subject: bitkeeper revision 1.891.1.14 (40a323c0nvrlljcyaqYaEcR8VMyfOQ) X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~18218^2~1 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/%22bookmarks://%22Dat/%22http:/www.example.com/cgi/%22https:/%22bookmarks:/%22Dat?a=commitdiff_plain;h=dd77060a9f8a7c799b431b1c405454d008a243ad;p=xen.git bitkeeper revision 1.891.1.14 (40a323c0nvrlljcyaqYaEcR8VMyfOQ) Forcibly reenable interrupts during exit-to-guest epilogue code in Xen. --- diff --git a/xen/arch/i386/entry.S b/xen/arch/i386/entry.S index 1fd1d9ebb0..b522f4f754 100644 --- a/xen/arch/i386/entry.S +++ b/xen/arch/i386/entry.S @@ -245,6 +245,10 @@ restore_all_guest: movsl movsl movsl + # Third, reenable interrupts. They will definitely be reenabled by IRET + # in any case. They could be disabled here if we are returning from an + # interrupt. We need interrupts enabled if we take a fault. + sti # Finally, restore guest registers -- faults will cause failsafe popl %ebx popl %ecx